⚡ Bolt: Optimize update_task JSON processing #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
⚡ Bolt: Optimize update_task JSON processing
💡 What:
Eliminated a redundant
jqprocess spawn inlib/task_manager/simple.sh'supdate_taskfunction. Previously, comma-separated values (tags, depends_on) were pre-processed by a separatejqinstance before being passed to the mainjqupdate command. Now, the raw string is passed to the mainjqcommand, which handles the splitting and trimming internally.🎯 Why:
Process spawning is expensive in shell scripts. Each
$(...)subshell and external command invocation adds overhead. In tight loops or frequent operations, this overhead accumulates.📊 Impact:
update_taskoperations.🔬 Measurement:
Run
benchmark.sh(created during development) or a similar loop callingupdate_taskrepeatedly.Verified that
tagsanddepends_onare still correctly parsed and updated.Ran existing tests in
tests/unit/test_task_manager.batsand confirmed no new regressions (existing failures are unrelated).PR created automatically by Jules for task 16922024910218443391 started by @oyi77